-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DocDiff: Cache remote content #441
Conversation
Realized we were "double triggering" the addon when the passed the GET arg, and now moved the state of enabled/disabled into the Addon. |
This should be working now 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates look good here 👍
Tests might be a good next addition, I'd tackle those in a separate PR though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with some small modifications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work! 🚀 💯
// This code isn't used until we show a UI, | ||
// and even then we'll want to trigger events to match state? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this code was used in the render()
method from above originally when I tried using a slider. We never deployed that, so we can probably remove that and this chunk as well.
HotKeys has to be initialized before DocDiff because when `?readthedocs-diff=true` DocDiff triggers an event that HotKeys has to listen to to update its internal state. * Related #645 * Related #441
Fixes #103